|
|
|
Contato/Contact:
Ministério da Defesa
Comando da Aeronáutica
|
Departamento de Controle
do Espaço Aéreo-DECEA
|
Av. Gen. Justo, 160
CEP 20021-130
Rio de Janeiro, RJ - Brasil
|
AFS: SBRJZXIC
|
|
|
AIC
|
A 36/2024
|
Publication Date/
Data de publicação:
|
28 NOV 2024
|
Effective date/
Data de efetivaçao:
|
28 NOV 2024
|
|
|
|
|
USE OF CONTROLLER-PILOT DATA LINK COMMUNICATIONS (CPDLC) IN THE BRAZILIAN CONTINENTAL AIRSPACE
|
|
1 PRELIMINARY ARRANGEMENTS
|
|
1.1. PURPOSE
This Aeronautical Information Circular (AIC) aims to disseminate the main information related to the use of Controller-Pilot Data Link Communications (CPDLC) in the Brazilian continental airspace.
The information contained in this Circular relates to the normative provisions contained in the specific publications of DECEA and in AIP- Brasil, Part ENR 3.3, Chapter 4 – Requirements and Special Procedures for ADS-C/CPDLC Operation of Aircraft in the Brazilian FIRs.
|
|
1.2. SCOPE
This circular applies to all those responsible for operating CPDLC and to SISCEAB users, where applicable.
|
|
1.3. ABBREVIATIONS
4DT 4D Trajectories
ACARS Aircraft Communication Addressing and Reporting System
ADS-C Automatic Dependent Surveillance - Contract
ATC Air Traffic Control
ATCO Air Traffic Controller
ATS Air Traffic Service
CPDLC Controller-Pilot Data Link Communications
CSP Communication Service Provider
DECEA Department of Airspace Control
FANS Future Air Navigation System
FIR Flight Information Region
FL Flight Level
FMS Flight Management System
ICAO International Civil Aviation Organization
PBCS Performance Based Communications and Surveillance
RCP Required Communication Performance
SATCOM Satellite Communication
SISCEAB Brazilian Airspace Control System
TBO Trajectory Based Operations
VDL VHF Data Link
VHF Very High Frequency
|
|
|
1.4.1. AIR TRAFFIC CONTROL CLEARANCE
Clearance for an aircraft to proceed under conditions specified by an ATC unit.
NOTE: For convenience, the term “AIR TRAFFIC CONTROL CLEARANCE” is often abbreviated to “CLEARANCE” when used in appropriate contexts.
|
1.4.2 CONTROLLER-PILOT DATA LINK COMMUNICATIONS (CPDLC)
|
Means of aeronautical communication between controller and pilot using data link for ATC communication.
|
1.4.3 DATA LINK COMMUNICATION
|
Form of communication intended for exchanging messages via data link.
|
|
Data link system certified to the requirements specified in RTCA DO-
258A/EUROCAE ED 100A, Interoperability Requirements for ATS Applications Using
ARINC 622 Data Communications (FANS 1/A INTEROP Standard), or earlier version.
NOTE: In FANS 1/A communications, the data link system of the aircraft, the ground
system of the ATS Unit and the Communication Service Provider agree with the
standard. In certain cases, specific reference is made to a particular type of FANS
1/A aircraft, as follows:
a) FANS 1/A+ means that the aircraft fully complies with Revision A of the
standard and includes the message latency monitor; and
b) FANS 1/A ADS-C means that the aircraft complies with the ADS-C
application, but does not include the CPDLC application.
|
1.4.5 BRAZILIAN CONTINENTAL AIRSPACE
|
Portion of the airspace under the responsibility of Brazil corresponding to the
Recife FIR, Amazônica FIR, Brasília FIR and Curitiba FIR.
|
1.4.6 CRITICAL SITUATION IN RELATION TO RESPONSE TIME
|
A situation in which immediate action by the air traffic controller and/or crew is
required during the provision of Air Traffic Services.
|
|
2.1 CPDLC is the means of communication between air traffic controllers and pilots using data
link for ATC communication. CPDLC includes a set of clearance/information/request
messages, in textual format, which correspond to the standard phraseology used in
radiotelephony.
|
NOTE: The CPDLC message elements used in Brazil are arranged in a specific Publication
of DECEA (MCA 100-23) based on Doc 4444 Air Traffic Management and Doc
10037 Global Operational Data Link (GOLD) Manual.
|
2.2 CPDLC is identified by ICAO as one of the enablers for the development of modern air
traffic management concepts (such as Trajectory Based Operations – TBO and 4D Trajectories
– 4DT), to ensure the maintenance of safety in air operations and enable greater organization,
predictability, fluidity, agility.
|
2.3 The implementation of the CPDLC has the potential to, in the short term:
|
a) mitigate problems of lack of understanding due to noise, interference,
language barriers, among others;
b) reduce voice channel congestion by improving the availability and efficiency
of the air-to-ground communications system;
c) reduce the workload of pilots and air traffic controllers, through the
automation of actions and the use of standardized messages;
d) allow the authorization of complex routes without the ATCO needing to
respond with manual entry of a long list of coordinates;
e) allow loading of route clearance information via CPDLC messages directly
into the FMS, minimizing the potential for data entry errors when issuing
ATC clearances.
|
|
3.1 CPDLC has been used at the Atlântico FIR as a primary means of communication since
2009.
|
3.2 With the objective of operationalizing the CPDLC in the Brazilian continental airspace,
DECEA established the Landell Project, whose main delivery, the beginning of the operational
use of the CPDLC in the Recife FIR and the Amazônica FIR, took place on September 9, 2021.
|
3.3 The initial operation of the CPDLC was in sectors 1, 2, 3, 4, 5, 6, 9 and 10 of the Recife FIR, and in sectors 1 to 5 of the Amazônica FIR (Belém Region).
|
3.4 On April 28, 2022, the use of the CPDLC was expanded to sectors 7, 8, 11 to 15 of the Recife FIR and on October 17, 2022 to sectors 6 to 15 of the Amazônica FIR.
|
3.5 The use of CPDLC in continental airspace is not mandatory. However, given the expected operational gains, DECEA strongly encourages fleet training and the use of the application.
|
3.6 Since the primary means for communication in the airspaces indicated in 3.3 and 3.4 is VHF, CPDLC is used as an additional means without affecting the applicable separation minima.
|
4 PLANNING FOR EXPANDING THE USE OF CPDLC
|
4.1 With a view to continuously improving the provision of air traffic services in Brazil,
DECEA plans to make the CPDLC operational in the Brasília FIR, starting in June 2023, and
in the Curitiba FIR, by the end of 2024 (Figure 1).
|
Figure 1 - Operational plan for the CPDLC in Brazilian continental airspace
|
4.2 The operationalization of the CPDLC in the Brasília FIR was planned in phases to allow
the gradual adaptation of ATCO and crews to the use of the system, as well as the verification of the behavior of the operation before widespread implementation.
|
4.3 The operationalization phases in the Brasília FIR will be applied in all sectors, according to the schedules below:
|
a) phase 1: from 0330Z to 0700Z;
b) phase 2: from 0330Z to 1500Z;
c) phase 3: from 2300Z to 1500Z; and
d) phase 4: no time restriction.
|
4.4 The operationalization of the CPDLC in the Curitiba FIR was adjusted to a single-phase implementation, in view of the characteristics of the FIR-CW sectors, the ease of
familiarization with the tool by ATCOs and crews, the history of training carried out and the consolidation of the system during its implementation in the national territory.
|
4.5 The operationalization phase at the Curitiba FIR will be as follows:
|
a) Single phase: All sectors, without time restrictions.
|
4.6 The dates for the start of each of the phases will be disclosed through NOTAM.
|
4.7 There will be no differences in operational or technical characteristics between Phases, with all CPDLC messages being applicable as provided for in MCA 100-23.
|
|
5.1 CPDLC is provided through a terrestrial communications infrastructure operated by SITA, through the ACARS network by the FANS 1/A data link system, using VDL Mode 2, VDL
Mode A and SATCOM subnets throughout the Brazilian airspace above FL250, inclusive.
|
NOTE 1: Only aircraft equipped with avionics compatible with the technologies described above will be able to establish a CPDLC connection.
NOTE 2: In continental Brazilian airspace, the CPDLC connection will only be possible if the aircraft with CPDLC capability is registered in the SITA network.
NOTE 3: Operators who have a contract with another CSP should check with their provider about the interoperability between the contracted service and the SITA service.
|
|
6.1 CPDLC will be available throughout Brazilian continental airspace, in accordance with item 4 of this Circular.
|
NOTE: Since the PBCS concept does not apply in Brazilian airspace, there is no RCP stipulation.
|
6.2 CPDLC will only be used in the Brazilian continental airspace where the ATS surveillance service is being provided. If an aircraft is out of sight, the aircraft will start to receive ATS
through voice communication, but it will not be necessary to interrupt the CPDLC connection.
|
NOTE: CPDLC should not be used for vectoring.
|
6.3 In continental airspace, the ADS-C connection is not necessary, as there is coverage by the ATS Surveillance system. Aircraft operators must instruct their crews, in accordance with their
operational standards, regarding the maintenance or disconnection of ADS-C in that airspace.
|
6.4 CPDLC will be used as an additional means to voice communication and should not be used in critical situations regarding response time. In this case, the use of voice should be
prioritized. Any situation that requires a prompt response from either party must be communicated via VHF.
|
NOTE: For urgent (PAN PAN) or emergency (MAYDAY) situations, priority shall be given to the use of voice communication. However, the crew may use CPDLC for emergency communications if deemed more convenient or if voice contact cannot be established.
|
6.5 In case of unavailability of the appropriate voice communication channel, the crew must adopt the communication failure procedures provided for in the DECEA rules. CPDLC may be
used to issue information and instructions in order to maintain flight safety until voice communication is reestablished.
|
6.6 Before entering a sector or FIR with CPDLC, the crew will be instructed, by voice or by CPDLC message, to make initial contact with the subsequent control unit, in order to guarantee
that the crew has performed the frequency change and that the transfer of communication has been effected. After initial contact, CPDLC communication shall be maintained unless ATC instructs otherwise.
|
|
7.1 For login, it is essential that the identification and registration of the aircraft are the same as the data entered in the FMS. It will not be possible to make the CPDLC connection if discrepancies are found.
|
7.2 The flight plan shall be filled out with the on-board capacity, using codes J3, J4, J5, J6 and/or J7, as provided for in MCA 100-11.
|
8 LOGON AND CONNECTION PROCEDURES
|
|
8.1. For the logon procedure, crews should use the addresses below:
a) Atlântico FIR: SBAO
b) Recife FIR: SBRE
c) Amazônica FIR: SBAZ
d) Brasília FIR: SBBS
e) Curitiba FIR: SBCW
|
8.2 Logon to CPDLC must be performed:
|
a) By aircraft taking off from an aerodrome within a FIR with CPDLC: before takeoff; or
b) By aircraft entering a FIR with CPDLC: at least 10 minutes and at most 25 minutes before entering the FIR.
NOTE: When moving between two FIRs with CPDLC, the transfer of connection must occur automatically. The crew must check the condition of the connection (active connection) with the system when crossing the FIR boundaries. If the automatic
transfer of connection does not occur, the crew must terminate the existing CPDLC connection and perform the procedure to establish a new connection, using the address of the corresponding FIR.
|
9 CREW OPERATIONAL PROCEDURES
|
|
9.1. It is essential that the crews are attentive to the uplink messages sent by ATS units and respond to them as quickly as possible. Delay in responding to an uplink message may result in a CPDLC disconnect.
|
|
9.2. If the crew notices the interruption of the CPDLC connection, it must inform the ATC unit using voice communication and follow the procedures for reconnection.
|
|
9.3. If an uplink message requires more detailed analysis for a response, the crew must respond as soon as possible with the STANDBY message, forwarding an appropriate reply after analysis. For example:
|
COMMUNICANT
|
INTENTION |
ACTION |
ATC unit
|
Check the shortest time or position
when a given flight level can be
accepted
|
Send message:
“WHEN CAN YOU ACCEPT FL350”
|
ACFT
|
Need to do a longer analysis to
respond to the request
|
IMMEDIATELY send a STANDBY
message
|
ACFT
|
Communicate the result of the
analysis
|
Send reply message:
WE CAN ACCEPT FL350 AT TIME
1245
|
|
|
9.4. When the pilot does not receive a response after sending a message, after a reasonable period, and without any error message having been received indicating failure in the transmission, he/she must send a message as indicated below.
NOTE 1: Alternatively, voice communication may be used.
NOTE 2: As reference, the air traffic control system uses a time delay of 45 seconds to alert the ATCO of non-receipt of a response to an uplink message.
|
COMMUNICANT
|
INTENTION |
ACTION |
ACFT
|
Flight level change request
(REQUEST CLIMB TO FL350)
already sent and no response
received.
|
Send message:
“WHEN CAN WE EXPECT FL350”
or voice communication.
|
|
|
|
10.1. The procedures related to the use of the Continental CPDLC and the progression of the application of the tool in the different airspace portions will be disseminated to SISCEAB users in due course through additional relevant publications.
|
|
10.2. This AIC republish the AIC A 18/24.
|
|
10.3. DECEA provides a communication channel for sending questions, suggestions, comments, criticisms, praise and error notifications through its Citizen Support Service (SAC) at the electronic address: http://servicos.decea.gov.br/sac/index.cfm, by selecting the CONTACT option in the Area menu.
|
|
10.4. Cases not provided for in this Circular shall be settled by the Head of DECEA’s Operations Subdepartment.
|